Profile-based conversion and delivery of electronic messages

ABSTRACT

A method, system and computer usable medium are disclosed for delivering an electronic message. A first computer is used to receive voice data from a user and to generate a message data file therefrom. A test is then conducted to determine whether a predetermined second computer is operably coupled to the communication network. If the result of the test indicates that the second computer is not coupled to the communication network, the message data file is forwarded to a predetermined storage location in an electronic messaging system. The message data file is subsequently retrieved from the predetermined storage location by the predetermined second computer and processed to comprise text data or voice mail data prior to forwarding to the predetermined storage location in the electronic messaging system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the disclosure relate in general to the field ofcomputers and similar technologies and, in particular, to softwareutilized in this field. More specifically, it relates to thetransmission of electronic messages using an instant messaging system.

2. Description of the Related Art

An instant messaging system (IMS) provides a simple way to exchangereal-time, text-based messages between users who are connected toon-line or electronic networking environments such as the Internet,intranets, and extranets. These systems, which have gained popularitydue to their simplicity and ease of use, require both sender andrecipient to be simultaneously logged-on to exchange messages. Usersthat are logged-on are typically indicated through visual cues, such asicons or text attributes (e.g., font, color, bold face, etc.). Byensuring that the recipient is available when a message is sent, themessage can be delivered and presented to the recipient nearlyinstantaneously.

To send an IMS message, a user generally logs on with an IMS client,selects one or more recipients from an address book of other IMS usersthat are currently on-line, and then composes and sends a message.However, there are situations where the requirement for IMS messagerecipients to be concurrently logged-on becomes problematic, such aswhen a message recipient's on-line status changes during an IMS session.For example, a sender may be typing a message to a recipient only todiscover that the recipient has gone off-line, resulting in the messagebeing rejected by the IMS.

There are cases when the sender's message is not time-critical and itwould be preferable to provide an alternative message delivery methodinstead of simply discarding the sender's message. For example, it maybe possible to reach a recipient email, text pager, or voicemail whenthey when they cannot be reached by an IMS. Current alternative IMSmessage delivery methods include conversion of IMS messages toalternative text formats for delivery to email or text pager systems.Other approaches include text-to-speech (TTS) conversion of IMS messagesfor delivery to a user's telephone or voicemail. However, there aretimes when these options are insufficient and it would be advantageousfor an IMS user to be able to generate a voice message while remainingon-line and without being required to place a separate phone call.

BRIEF SUMMARY OF THE INVENTION

A method, system and computer usable medium are disclosed for deliveringan electronic message. In various embodiments of the invention a firstcomputer is used to receive voice data from a user and to generate amessage data file therefrom. A test is then conducted to determinewhether a predetermined second computer is operably coupled to thecommunication network. If the result of the test indicates that thesecond computer is not coupled to the communication network, the messagedata file is forwarded to a predetermined storage location in anelectronic messaging system. In various embodiments of the invention,the message data file is subsequently retrieved from the predeterminedstorage location by the predetermined second computer.

In some embodiments of the invention, the message data file is processedto comprise text data prior to forwarding to the predetermined storagelocation in the electronic messaging system. In some embodiments, thetext data in the message data file is displayed on a user interfacedevice coupled to the first computer prior to being forwarded to thepredetermined storage location in the electronic messaging system.

In other embodiments of the invention, the message data file isprocessed to comprise voicemail data prior to forwarding to thepredetermined storage location in the electronic messaging system. Insome embodiments, the voicemail data is formatted to comprise a voiceover internet protocol (VoIP) format prior to forwarding to thepredetermined storage location.

BRIEF DESCRIPTION OF THE DRAWINGS

Selected embodiments of the present invention may be understood, and itsnumerous objects, features and advantages obtained, when the followingdetailed description is considered in conjunction with the followingdrawings, in which:

FIG. 1 depicts an exemplary client computer in which the presentinvention may be implemented;

FIG. 2 is a simplified block diagram of an instant messaging system(IMS) as implemented in accordance with an embodiment of the invention;

FIG. 3 is a generalized illustration of an IMS user interface asimplemented in accordance with an embodiment of the invention;

FIG. 4 is a generalized illustration of an IMS user interface asimplemented with user-selectable voice profile attributes in accordancewith an embodiment of the invention; and

FIGS. 5 a-c are a generalized flowchart of an instant messaging system500 as implemented in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

A method, system and program are disclosed for delivering an electronicmessage in non-real-time to an alternative electronic messaging system(EMS). As will be appreciated by one skilled in the art, the presentinvention may be embodied as a method, system, or computer programproduct. Accordingly, embodiments of the invention may be implementedentirely in hardware, entirely in software (including firmware, residentsoftware, micro-code, etc.) or in an embodiment combining software andhardware. These various embodiments may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, the presentinvention may take the form of a computer program product on acomputer-usable storage medium having computer-usable program codeembodied in the medium.

Any suitable computer usable or computer readable medium may beutilized. The computer-usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, device,or propagation medium. More specific examples (a non-exhaustive list) ofthe computer-readable medium would include the following: an electricalconnection having one or more wires, a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a transmission media such as those supportingthe Internet or an intranet, or a magnetic storage device. In thecontext of this document, a computer-usable or computer-readable mediummay be any medium that can contain, store, communicate, propagate, ortransport the program for use by or in connection with the instructionexecution system, apparatus, or device.

Computer program code for carrying out operations of the presentinvention may be written in an object oriented programming language suchas Java, Smalltalk, C++ or the like. However, the computer program codefor carrying out operations of the present invention may also be writtenin conventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Embodiments of the invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

FIG. 1 is a block diagram of an exemplary client computer 102 in whichthe present invention may be utilized. Client computer 102 includes aprocessor unit 104 that is coupled to a system bus 106. A video adapter108, which controls a display 110, is also coupled to system bus 106.System bus 106 is coupled via a bus bridge 112 to an Input/Output (I/O)bus 114. An I/O interface 116 is coupled to I/O bus 114. The I/Ointerface 116 affords communication with various I/O devices, includinga keyboard 118, a mouse 120, a Compact Disk-Read Only Memory (CD-ROM)drive 122, a floppy disk drive 124, and a flash drive memory 126. Theformat of the ports connected to I/O interface 116 may be any known tothose skilled in the art of computer architecture, including but notlimited to Universal Serial Bus (USB) ports.

Client computer 102 is able to communicate with a service providerserver 152 via a network 128 using a network interface 130, which iscoupled to system bus 106. Network 128 may be an external network suchas the Internet, or an internal network such as an Ethernet Network or aVirtual Private Network (VPN). Using network 128, client computer 102 isable to use the present invention to access service provider server 152.

A hard drive interface 132 is also coupled to system bus 106. Hard driveinterface 132 interfaces with a hard drive 134. In a preferredembodiment, hard drive 134 populates a system memory 136, which is alsocoupled to system bus 106. Data that populates system memory 136includes the client computer's 102 operating system (OS) 138 andapplication programs 144.

OS 138 includes a shell 140 for providing transparent user access toresources such as application programs 144. Generally, shell 140 is aprogram that provides an interpreter and an interface between the userand the operating system. More specifically, shell 140 executes commandsthat are entered into a command line user interface or from a file.Thus, shell 140 (as it is called in UNIX®), also called a commandprocessor in Windows®, is generally the highest level of the operatingsystem software hierarchy and serves as a command interpreter. The shellprovides a system prompt, interprets commands entered by keyboard,mouse, or other user input media, and sends the interpreted command(s)to the appropriate lower levels of the operating system (e.g., a kernel142) for processing. While shell 140 generally is a text-based,line-oriented user interface, the present invention can also supportother user interface modes, such as graphical, voice, gestural, etc.

As depicted, OS 138 also includes kernel 142, which includes lowerlevels of functionality for OS 138, including essential servicesrequired by other parts of OS 138 and application programs 144,including memory management, process and task management, diskmanagement, and mouse and keyboard management.

Application programs 144 may include a browser 146 and email client 148.Browser 146 includes program modules and instructions enabling a WorldWide Web (WWW) client (i.e., client computer 102) to send and receivenetwork messages to the Internet using HyperText Transfer Protocol(HTTP) messaging, thus enabling communication with service providerserver 152. Application programs 144 also include an instant messagingclient 150. Instant messaging client 150 includes code for implementingthe processes described in FIGS. 2 through 5 described hereinbelow. Inone embodiment, client computer 102 is able to download instantmessaging client 150 from a service provider server 152.

The hardware elements depicted in client computer 102 are not intendedto be exhaustive, but rather are representative to highlight componentsused by the present invention. For instance, client computer 102 mayinclude alternate memory storage devices such as magnetic cassettes,Digital Versatile Disks (DVDs), Bernoulli cartridges, and the like.These and other variations are intended to be within the spirit andscope of the present invention.

FIG. 2 is a simplified block diagram of an instant messaging system(IMS) 200 as implemented in accordance with embodiments of theinvention. In various embodiments, an instant messaging system (IMS)session is begun with an IMS message sender 202 accessing IMS system208, which comprises an IMS recipient registry 210. In one embodiment,the IMS recipient registry 210 indicates that IMS message recipients ‘A’220 and ‘B’ 224 are currently on-line, while IMS message recipient ‘C’228 is not. In these embodiments, IMS recipient registry 210 alsocomprises message delivery information, including delivery information212 used for non-real-time delivery of IMS messages to off-line IMSmessage recipient ‘C’ 228. In one embodiment, the message deliveryinformation comprises voicemail address, format and communicationprotocol information. In another embodiment, the message deliveryinformation comprises electronic mail (email) address, format andcommunication protocol information.

The IMS message sender 202 begins an IMS session by selecting on-lineIMS message recipients ‘A’ 220 and ‘B’ 224, and off-line recipient ‘C’228 from the IMS recipient registry. During the IMS session, IMS messagesender 202 enters text into a user interface window of an IMS clientapplication (not shown) running on IMS sender computer 204. The enteredtext is received by the IMS 208, which references the IMS recipientregistry 210 to determine the intended IMS message recipient ‘A’ 220,‘B’ 224 or ‘C’ 228. Using the message delivery information contained inthe IMS recipient registry 210, the IMS 208 uses the Internet 214 todeliver the text entered by IMS sender 202 as a real-time text messageto the intended on-line IMS message recipient's computer ‘A’ 222 or ‘B’226. Since IMS message recipient ‘C’ 228 is indicated to be off-line bythe IMS recipient registry 210, the IMS sender 202 is given the optionof delivering an IMS message using an alternative or non-real-time IMSmessage delivery method.

In one embodiment, the IMS message sender 202 records a voice message byspeaking into a microphone 206 coupled to an IMS client application (notshown) running on IMS sender computer 204. In this embodiment, the IMSmessage sender 202 records, pauses, replays, edits, cancels and performsother voice message operations through user gestures with the userinterface of the IMS client application. Through implementation of thesevoice message operations, the IMS sender 202 can review an audio versionof the voice message prior to its non-real-time delivery to IMS messagerecipient ‘C’ 228. In one embodiment, speech-to-text conversionoperations familiar to those of skill in the art are performed, and theconverted text is displayed within a window of the IMS clientapplication. Once displayed, the IMS message sender 202 can review theconverted text of the voice message and make desired revisions prior tothe non-real-time delivery of the voice message to the off-line IMSmessage recipient ‘C’ 228. After the voice message is reviewed and anydesired revisions are completed, the IMS message sender uses the messagedelivery information of IMS recipient ‘C’ 212 to select routing of thevoice message to voicemail messaging system 218. The IMS 208 uses themessage delivery information to route the voice message through theInternet 214, and in turn through the public switched telephone network(PSTN) 216, to the voice mail messaging system 218. The voicemailmessaging system 218 receives the voice message and stores it as avoicemail in a voice mailbox assigned to IMS recipient ‘C’ 228. In oneembodiment, the voicemail messaging system 218 uses one or more methodsfamiliar to those of skill in the art to notify the IMS recipient ‘C’228 that a voicemail has been received. The IMS recipient ‘C’ 228 thenuses telephone 232 to accesses the voicemail messaging system 218 andretrieve the voice message from their voice mailbox.

In another embodiment the IMS message sender 202 composes a text messagewithin the IMS client application for conversion into a synthesizedvoice message that will be delivered to the voicemail messaging system218 in non-real-time. In this embodiment, the IMS message recipient ‘C’228 is either off-line, real-time delivery of the message is notnecessary, or the IMS message sender 202 may prefer that the IMS textmessage be delivered as a voice message. Accordingly, the IMS messagesender 202 composes, reviews, and edits the text message within a windowof the IMS client application running on the IMS sender computer 210.Once the IMS message sender 202 completes composition of the IMS textmessage, text-to-speech conversion operations familiar to those of skillin the art are performed by the IMS 208. The IMS 208 then usesassociated message delivery information to deliver the converted IMStext message in non-real-time as a voice message to the voice mailmessaging system 218. The voicemail messaging system 218 receives thevoice message and stores it as a voicemail in a voice mailbox assignedto IMS recipient ‘C’ 228. The IMS recipient ‘C’ 228 then uses telephone232 to accesses the voicemail messaging system 218 and retrieve thevoice message from their voice mailbox.

In yet another embodiment, the IMS message sender 202 composes a textmessage within the IMS client application for delivery to thealternative electronic messaging system 234 (e.g., an email system) innon-real-time. In this embodiment, the IMS message recipient ‘C’ 228 iseither off-line, real-time delivery of the message is not necessary, orthe IMS message sender 202 may prefer that the IMS text message bedelivered through the alternative electronic messaging system 234.Accordingly, the IMS message sender 202 composes, reviews, and edits thetext message within a window of the IMS client application running onthe IMS sender computer 210. Once the IMS message sender 202 completescomposition of the IMS text message, text-to-text conversion operationsfamiliar to those of skill in the art are performed by the IMS 208. TheIMS 208 then uses associated message delivery information to deliver theconverted IMS text message in non-real-time to the alternativeelectronic messaging system 234. The alternative electronic messagingsystem 234 receives the converted text message and stores it as a nativetext message in a text message mailbox assigned to IMS recipient ‘C’228. The IMS recipient ‘C’ computer 234 is then used by IMS recipient‘C’ to access the alternative electronic messaging system 234 andretrieve the text message from their text message mailbox.

FIG. 3 is a generalized illustration of an instant messaging system(IMS) user interface 300 as implemented in accordance with an embodimentof the invention.

In various embodiments, an IMS client is implemented to present an IMSuser interface (UI) 302 to the users of an IMS. In these embodiments,the IMS UI 302 comprises IMS directory window 304, IMS message window306, and speech conversion window 308. The IMS UI 302 further comprisesIMS user controls for IMS message operations, including “send” 310,“cancel” 312, “clear” 314, along with “record voice message” button 318and “voice message recording control icons” 320, which are used forrecording voice messages.

An IMS message sender initiates an instant messaging system (IMS)session by accessing an IMS system through the IMS UI 302. Afterconnecting to the IMS, the contents of an IMS recipient registry aredisplayed in IMS directory window 304, including IMS recipients andtheir IMS connection status. In various embodiments, additional IMSrecipient registry content is displayed in IMS directory window 304,including message delivery information used for non-real-time deliveryof IMS messages to off-line IMS message recipients. In one embodiment,the message delivery information comprises voicemail address, format andcommunication protocol information. In another embodiment, the messagedelivery information comprises electronic mail (email) address, formatand communication protocol information.

Once the IMS session is initiated, the IMS message sender selectson-line and off-line IMS message recipients within the IMS directorywindow 304 through a user gesture such as a mouse click. In oneembodiment, text attributes such as a bold, italic, or color are appliedto IMS recipient entries within the IMS UI 304 to indicate whichrecipients have been selected by the IMS message sender to receive anIMS message. In another embodiment, similar attributes are applied toIMS recipient entries to designate alternative or non-real-time IMSmessage delivery methods.

As an example, “Joe”, “John”, “Paul”, “Robert” and “Sarah” are indicatedto be selected for receipt of IMS messages by the application of a boldtext attribute to their IMS recipient “name” and “status” entries withinthe IMS UI 304. However, “John,” “Paul,” “Robert” and “Sarah” arecurrently on-line, with the result that an italic text attribute isadditionally applied to their recipient “name” and “status” entries.Conversely, “Joe” is off-line, result that an italic text attribute isnot additionally applied to his recipient “name” and “status” entry. Inthis example, the same text attributes are similarly applied to theirrespective recipient entries for a default “message delivery method.”Since “John,” “Paul,” “Robert” and “Sarah” are currently on-line, theirdefault message delivery method is designated as “IMS,” whereas “Joe,”who is currently off-line, is designated to receive IMS messages via“voicemail.”

During the IMS session, the IMS message sender enters text into the IMSmessage window 306 of IMS UI 304 and uses user controls 310, 312 and 314to control the sending of IMS text messages. The entered text isreceived by the IMS, which references the IMS recipient registry todetermine the intended IMS message recipient. Using the message deliveryinformation contained in the IMS recipient registry, the IMS deliversthe entered text as a real-time text message to the intended on-line IMSmessage recipient. If an intended IMS message recipient is off-line, theIMS sender is given the option of delivering an IMS message using analternative or non-real-time IMS message delivery method.

In one embodiment, the IMS message sender records a voice message byspeaking into a microphone coupled to their IMS client application. Inthis embodiment, the IMS message sender records a voice message by usingthe “record voice message” button 318 and “voice message recordingcontrol icons” 320 to perform record, pause, replay, edit, cancel andother voice message operations. Implementation of these voice messageoperations allows the IMS sender to review an audio version of the voicemessage prior to its non-real-time delivery to on off-line IMS messagerecipient. In one embodiment, speech-to-text conversion operationsfamiliar to those of skill in the art are performed, and the convertedtext is displayed within speech conversion window 308. Once displayed,the IMS message sender can review the converted text of the voicemessage and make desired revisions prior to the non-real-time deliveryof the voice message to the off-line IMS message recipient. After thevoice message is reviewed and any desired revisions are completed, theIMS message sender selects “voicemail” through a user gesture within IMSdirectory window 304 as the desired “message delivery method” for theoff-line recipient. The IMS then uses the associated message deliveryinformation stored within the IMS recipient registry to route the voicemessage to the corresponding voice mail messaging system. In turn, thevoicemail messaging system receives the voice message and stores it as avoicemail in a voice mailbox assigned to the selected off-line IMSmessage recipient. The off-line IMS message recipient then accesses thevoicemail messaging system and retrieves the voice message from theirvoice mailbox.

In another embodiment, the IMS message sender composes a text messagewithin the IMS message window 306 for conversion into a synthesizedvoice message that will be delivered to a voicemail messaging system innon-real-time. In this embodiment, the IMS message recipient is eitheroff-line, real-time delivery of the message is not necessary, or the IMSmessage sender may prefer that the IMS text message be delivered as avoice message. Accordingly, the IMS message sender composes, reviews,and edits the text message within the IMS message window 306. Once theIMS message sender completes composition of the IMS text message,text-to-speech conversion operations familiar to those of skill in theart are performed by the IMS. The IMS then uses associated messagedelivery information stored within the IMS recipient registry to deliverthe converted IMS text message in non-real-time as a voice message tothe IMS message recipient's voice mail messaging system. In turn, thevoicemail messaging system receives the voice message and stores it as avoicemail in a voice mailbox assigned to the selected off-line IMSmessage recipient. The off-line IMS message recipient then accesses thevoicemail messaging system and retrieves the voice message from theirvoice mailbox.

In yet another embodiment, the IMS message sender composes a textmessage within the IMS message window 306 for conversion into a textmessage that will be delivered to an alternative electronic messagingsystem (e.g., an email system) in non-real-time. In this embodiment, theIMS message recipient is either off-line, real-time delivery of themessage is not necessary, or the IMS message sender may prefer that theIMS text message be delivered through the alternative electronicmessaging system. Accordingly, the IMS message sender composes, reviews,and edits the text message within the IMS message window 306. Once theIMS message sender completes composition of the IMS text message,text-to-text conversion operations familiar to those of skill in the artare performed by the IMS. The IMS then uses associated message deliveryinformation stored within the IMS recipient registry to deliver theconverted IMS text message in non-real-time to the alternativeelectronic messaging system. The alternative electronic messaging systemreceives the converted text message and stores it as a native textmessage in a text message mailbox assigned to the IMS message recipient.The IMS recipient then accesses the alternative electronic messagingsystem and retrieves the text message from their text message mailbox.

FIG. 4 is a generalized illustration of an instant messaging system(IMS) user interface 400 as implemented with user-selectable voiceprofile attributes in accordance with an embodiment of the invention. Invarious embodiments, an IMS client is implemented to present an IMS userinterface (UI) 302 to the users of an IMS. In these embodiments, the IMSUI 302 comprises IMS directory window 304, IMS message window 306,speech conversion window 308, and IMS speech profile window 418. The IMSUI 302 further comprises IMS user controls for IMS message operations,including “send” 310, “cancel” 312, “clear” 314, “apply profile” 416,along with “record voice message” button 318 and “voice messagerecording control icons” 320, which are used for recording voicemessages. IMS speech profile window 418 further comprises speech profilecontrol buttons “apply” 420, “save” 422, “cancel” 424, “import” 428, andspeech profile attributes 428.

An IMS message sender initiates an instant messaging system (IMS)session by accessing an IMS system through the IMS UI 302. Afterconnecting to the IMS, the contents of an IMS recipient registry aredisplayed in IMS directory window 304, including IMS recipients andtheir IMS connection status. Once the IMS session is initiated, the IMSmessage sender selects on-line and off-line IMS message recipientswithin the IMS directory window 304 through a user gesture such as amouse click. In one embodiment, text attributes such as a bold, italic,or color are applied to IMS recipient entries within the IMS UI 304 toindicate which recipients have been selected by the IMS message senderto receive an IMS message. In another embodiment, similar attributes areapplied to IMS recipient entries to designate alternative ornon-real-time IMS message delivery methods.

During the IMS session, the IMS message sender enters text into the IMSmessage window 306 of IMS UI 304 and uses user controls 310, 312 and 314to control the sending of IMS text messages. The entered text isreceived by the IMS, which references the IMS recipient registry todetermine the intended IMS message recipient. Using the message deliveryinformation contained in the IMS recipient registry, the IMS deliversthe entered text as a real-time text message to the intended on-line IMSmessage recipient. If an intended IMS message recipient is off-line, theIMS sender is given the option of delivering an IMS message using analternative or non-real-time IMS message delivery method.

In another embodiment the IMS message sender composes a text messagewithin the IMS message window 306 for conversion into a synthesizedvoice message that will be delivered to a voicemail messaging system innon-real-time. In this embodiment, the IMS message recipient is eitheroff-line, real-time delivery of the message is not necessary, or the IMSmessage sender may prefer that the IMS text message be delivered as avoice message. Accordingly, the IMS message sender composes, reviews,and edits the text message within the IMS message window 306 and thenselects voice profile attributes within the IMS speech profile window418.

In one embodiment, the IMS message sender selects gender (e.g., male,female), age (child, teen, adult, etc.), and style (question, happy,sad, etc.) speech profile attributes 428 which are applied to the IMStext during to its conversion to a voice message. In another embodiment,personality voices (e.g., cartoon characters, movie stars, etc.) arelikewise applied to the IMS text. The application of these voice profileattributes allows the IMS message sender to create a synthesized voicemessage tone and style for the voice message that will be delivered innon-real-time to the IMS message recipient. Many such voice profileattribute combinations are possible and the foregoing examples areneither exhaustive nor intended to constrain the possible combinationsthat are implementable in different embodiments of the invention. Inanother embodiment, voice profile attributes are imported for use by theIMS system.

The selected voice profile attributes are then applied to the IMSmessage text during text-to-speech conversion operations familiar tothose of skill. Text-to-speech conversion operations are then performedby the IMS to generate a synthesized voice message with the desiredspeech profile attributes. The IMS then uses associated message deliveryinformation stored within the IMS recipient registry to deliver theconverted IMS text message in non-real-time as a voice message to theIMS message recipient's voice mail messaging system. In turn, thevoicemail messaging system receives the voice message and stores it as avoicemail in a voice mailbox assigned to the selected off-line IMSmessage recipient. The off-line IMS message recipient then accesses thevoicemail messaging system and retrieves the voice message from theirvoice mailbox.

FIGS. 5 a-c are a generalized flow chart of an instant messaging system500 as implemented in accordance with an embodiment of the invention. Invarious embodiments, an instant messaging system (IMS) session is begunin step 502 with an IMS message sender accessing an IMS recipientregistry in step 504. In one embodiment, the IMS recipient registryindicates which IMS message recipients are currently on-line and alsocomprises message delivery information for non-real-time delivery of IMSmessages to off-line IMS message recipients. In one embodiment, themessage delivery information comprises voicemail address, format andcommunication protocol information. In another embodiment, the messagedelivery information comprises electronic mail (email) address, formatand communication protocol information. In step 506, the IMS messagesender selects IMS message recipients from the IMS recipient registryand ongoing IMS monitoring is begun in step 508 to determine if any ofthe selected IMS message recipients are off-line.

If it is determined in step 510 that none of the selected IMS messagerecipients are off-line, then IMS session operations are conducted instep 512. A determination is made in step 514 whether there are anyqueued IMS messages requiring alternative or non-real-time delivery toone or more electronic messaging systems. If there are, then they aredelivered in step 516. Otherwise, or after the queued IMS messages aredelivered alternatively or in non-real-time, a determination is made instep 518 whether to end the IMS session. If it is decided to not end theIMS session, then the process is repeated, beginning with step 508.Otherwise, the IMS session is ended in step 566.

However, if it is determined in step 510 that one or more of theselected IMS messaged recipients are off-line, then a decision is madein step 520 whether to implement an alternative or non-real-time IMSmessage delivery method. If it is decided in step 520 to not to choosean alternative or non-real-time IMS message delivery method, then IMSsession operations are conducted in step 512. A determination is made instep 514 whether there are any queued IMS messages requiring alternativeor non-real-time delivery to one or more electronic messaging systems.If there are, then they are delivered in step 516. Otherwise, or afterthe queued IMS messages are delivered alternatively or in non-real-time,a determination is made in step 518 whether to end the IMS session. Ifit is decided to not end the IMS session, then the process is repeated,beginning with step 508. Otherwise, the IMS session is ended in step566.

If it is decided in step 520 to implement an alternative ornon-real-time IMS message delivery method for off-line IMS messagerecipients, then a first off-line IMS message recipient is selected instep 522. Once selected, the alternative IMS message delivery method forthe selected IMS message recipient is determined in step 524. If it isdetermined that a voice message will be generated for non-real-timedelivery, then the IMS message sender records a voice message in step526. In one embodiment, the IMS message sender records a voice messageby speaking into a microphone coupled to the IMS client applicationrunning on their computer. In this embodiment, the IMS message senderrecords, pauses, replays, edits, cancels and performs other voicemessage operations through user gestures with the user interface of theIMS client application. Through implementation of these voice messageoperations, the IMS sender can review an audio version of the voicemessage prior to its non-real-time delivery to the selected IMS messagerecipient. If it is determined in step 528 that the voice message is notyet complete, then voice message operations continue, beginning withstep 526.

Once voice message operations are completed, it is then determined instep 530 whether to convert the recorded voice message into text. If itis decided in step 530 to convert the recorded voice message into text,then speech-to-text conversion operations familiar to those of skill inthe art are performed in step 532. In one embodiment, the converted textis displayed within a window of the IMS client application. Oncedisplayed, the IMS message sender can review the converted text of thevoice message prior to its non-real-time delivery to the selected IMSmessage recipient.

After speech-to-text conversions are performed in step 532, or if it isdetermined in step 524 to select text as an alternative or non-real-timeIMS message delivery method, then it is determined in step 534 whetherto IMS text conversion is required. If it is determined in step 534 thatIMS text conversion is not required, then a determination is made instep 536 whether the IMS text will be delivered in non-real-time as anIMS text message to the IMS message recipient. If it is determined instep 536 to not deliver the IMS text in non-real-time, then the processis repeated beginning with step 520, where a determination is madewhether an alternative or non-real-time delivery method is chosen for anoff-line IMS message recipient. Otherwise, the IMS text is queued fornon-real-time IMS system delivery to the IMS message recipient in step538. It is then determined in step 540 whether additional IMS messagerecipients will be selected for alternative or non-real-time delivery ofIMS messages. If it is determined in step 540 to select additional IMSmessage recipients, then the process is continued beginning with step522, with the selection of an additional recipient for alternative IMSmessage delivery. Otherwise, the process is repeated beginning with step512, where IMS session operations are conducted as described in greaterdetail herein.

However, if it is determined in step 534 that IMS text conversion isrequired, then it is determined in step 542 whether to convert the textof the IMS message into a voice message. If it is determined in step 542that the text of the IMS message is not to be converted into a voicemessage, then an alternative text message delivery method anddestination are selected in step 544. Once selected, conversionoperations are performed on the IMS message text to convert it into therequired format and communication protocol in step 546. In oneembodiment, the IMS text message is converted into an email message thatis deliverable in non-real-time to an email address for retrieval by theIMS message recipient. Once conversion operations are completed in step548, the converted IMS text message is queued for non-real-time deliveryin step 548. It is then determined in step 540 whether additional IMSmessage recipients will be selected for alternative or non-real-timedelivery of IMS messages. If it is determined in step 540 to selectadditional IMS message recipients, then the process is continuedbeginning with step 522, with the selection of an additional recipientfor alternative IMS message delivery. Otherwise, the process is repeatedbeginning with step 512, where IMS session operations are conducted asdescribed in greater detail herein.

However, if it is determined in step 542 that the IMS message text is tobe converted into a voice message, then a determination is made in step550 whether voice profile attributes are to be applied to the IMSmessage text during text-to-speech conversion operations. If it isdetermined in step 550 that voice profile attributes are to be applied,then a determination is made in step 552 whether voice profileattributes are to be imported. If voice profile attributes are to beimported, they are imported in step 554 and made available for use bythe IMS system. Otherwise, the IMS message sender selects and appliesthe voice profile attributes to the IMS message text in step 556. In oneembodiment, the IMS message sender selects gender (e.g., male, female),their age (child, teen, adult, etc.), and style (question, happy, sad,etc.) attributes which can be applied to the IMS text during itsconversion to a voice message. In another embodiment, personality voices(e.g., cartoon characters, movie stars, etc.) can be likewise applied tothe IMS text. The application of these voice profile attributes allowsthe IMS message sender to create a synthesized voice message tone andstyle for the voice message that will be delivered in non-real-time tothe IMS message recipient. Many such voice profile attributecombinations are possible and the foregoing examples are neitherexhaustive nor intended to constrain the possible combinations that areimplementable in different embodiments of the invention.

Once voice profile attributes have been selected and applied in step556, or if it is determined in step 550 to not apply voice profileattributes, then text-to-speech operations familiar to those of skill inthe art are performed in step 558. In one embodiment, the IMS messagesender composes a text message within the IMS client application forconversion into a synthesized voice message that will be delivered tothe IMS message recipient's voicemail system in non-real-time. In thisembodiment, the IMS message recipient is either off-line, real-timedelivery of the message is not necessary, or the IMS message sender mayprefer that the IMS text message be delivered as a voice message.Accordingly, the IMS message sender composes, reviews, and edits thetext message within a window of the IMS client application. Once the IMSmessage sender completes composition of the IMS text message,text-to-speech conversion operations familiar to those of skill in theart are performed. The resulting converted IMS text message is deliveredas a voice message to a predetermined voice mail box for retrieval bythe IMS message recipient.

After text-to-speech conversions are performed in step 558, or if it isdetermined in step 530 that speech-to-text conversion operations are notrequired, then the IMS message sender confirms the voice mail format,destination and transport protocol in step 560. In one embodiment, thevoice message is formatted into a predetermined audio format such aswaveform audio format (.wav), audio file format (.au), or audiointerchange file format (.aiff). In another embodiment, thepredetermined audio output format comprises the voice over Internetprotocol (VoIP) format. Many such combinations are possible and theforegoing examples are neither exhaustive nor intended to constrain thepossible combinations of audio formats or communication protocols thatare implementable in different embodiments of the invention. After voicemessage format, destination and transport protocol is confirmed in step560, the voice message is signed with the user ID of the IMS messagesender in step 562. The voice message is then queued for non-real-timedelivery to its destination in step 564. If it is determined in step 540to select additional IMS message recipients, then the process iscontinued beginning with step 522 with the selection of an additionalrecipient for alternative IMS message delivery. Otherwise, the processis repeated beginning with step 512, where IMS session operations areconducted as described in greater detail herein.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of skill in the art withoutdeparting from the scope and spirit of the invention. The embodiment waschosen and described in order to best explain the principles of theinvention and the practical application, and to enable others of skillin the art to understand the invention for various embodiments withvarious modifications as are suited to the particular use contemplated.

Having thus described the invention of the present application in detailand by reference to preferred embodiments thereof, it will be apparentthat modifications and variations are possible without departing fromthe scope of the invention defined in the appended claims.

1. A computer-implemented method for delivering an instant message,comprising: storing instant message recipient data in a recipientregistry, wherein said instant message recipient data comprises: apreferred electronic message delivery format associated with an instantmessage recipient, wherein said preferred electronic message deliveryformat for use when said instant message recipient is unable to receivesaid instant message; and storage location data associated with anelectronic messaging system storage location associated with saidpreferred electronic message delivery format; receiving instantmessage-data from an instant message originator, wherein said instantmessage data is processed to generate an instant message for receipt bysaid instant message recipient; determining whether said instant messagerecipient is able to receive said instant message; processing saidinstant message recipient data to determine said message recipient'spreferred message delivery format upon determination that said instantmessage recipient is unable to receive said instant message; andprocessing said instant message to convert said instant message intosaid preferred message delivery format, wherein said instant message isstored in said preferred message delivery format in said associatedelectronic messaging system storage location.
 2. The method of claim 1,wherein said instant message is subsequently retrieved in said preferredmessage delivery format from said preferred electronic messaging systemstorage location by said instant message recipient.
 3. The method ofclaim 1, wherein said preferred electronic message delivery formatcomprises electronic mail data.
 4. The method of claim 3, wherein textdata in said instant message is edited by said instant messageoriginator prior to being converted into said preferred electronicmessage delivery format.
 5. The method of claim 1, wherein saidpreferred message delivery format comprises voicemail data.
 6. Themethod of claim 5, wherein said preferred message delivery formatcomprises voicemail data.
 7. A system for delivering an electronicmessage using a first computer connected to a communication network,said first computer comprising: a processor; a data bus coupled to theprocessor; and a non-transitory computer-usable storage medium embodyingcomputer program code, the non-transitory computer-usable storage mediumbeing coupled to the data bus, the computer program code for deliveringan instant message and comprising instructions executable by theprocessor and configured for: storing instant message recipient data ina recipient registry, wherein said instant message recipient datacomprises: a preferred electronic message delivery_format associatedwith an instant message recipient, wherein said preferred electronicmessage delivery format for use when said instant message recipient isunable to receive said instant message; and storage location dataassociated with an electronic messaging system storage locationassociated with said preferred electronic message delivery format;receiving instant message-data from an instant message originator,wherein said instant message data is processed to generate an instantmessage for receipt by said instant message recipient; determiningwhether said instant message recipient is able to receive said instantmessage; processing said instant message recipient data to determinesaid message recipient's preferred message delivery format upondetermination that said instant message recipient is unable to receivesaid instant message; and processing said instant message to convertsaid instant message into said preferred message delivery format,wherein said instant message is stored in said preferred messagedelivery format in said associated electronic messaging system storagelocation.
 8. The system of claim 7, wherein said instant message issubsequently retrieved in said preferred message delivery format fromsaid preferred electronic messaging system storage location by saidinstant message recipient.
 9. The system of claim 1, wherein saidpreferred electronic message delivery format comprises electronic maildata.
 10. The system of claim 9, wherein text data in said instantmessage is edited by said instant message originator prior to beingconverted into said preferred electronic message delivery format. 11.The system of claim 1, wherein said preferred message delivery formatcomprises voicemail data.
 12. The system of claim 11, wherein saidpreferred message delivery format comprises voicemail data.
 13. Anon-transitory computer-readable storage medium embodying computerprogram code for use by a first computer coupled to a communicationsystem, the computer program code comprising computer executableinstructions configured for: storing instant message recipient data in arecipient registry, wherein said instant message recipient datacomprises: a preferred electronic message delivery format associatedwith an instant message recipient, wherein said preferred electronicmessage delivery format for use when said instant message recipient isunable to receive said instant message; and storage location dataassociated with an electronic messaging system storage locationassociated with said preferred electronic message delivery format;receiving instant message-data from an instant message originator,wherein said instant message data is processed to generate an instantmessage for receipt by said instant message recipient; determiningwhether said instant message recipient is able to receive said instantmessage; processing said instant message recipient data to determinesaid message recipient's preferred message delivery format upondetermination that said instant message recipient is unable to receivesaid instant message; and processing said instant message to convertsaid instant message into said preferred message delivery format,wherein said instant message is stored in said preferred messagedelivery format in said associated electronic messaging system storagelocation.
 14. The non-transitory computer-usable medium of claim 13,wherein said instant message is subsequently retrieved in said preferredmessage delivery format from said preferred electronic messaging systemstorage location by said instant message recipient.
 15. Thenon-transitory computer-usable medium of claim 13, wherein saidpreferred electronic message delivery format comprises electronic maildata.
 16. The non-transitory computer-usable medium of claim 15, whereintext data in said instant message is edited by said instant messageoriginator prior to being converted into said preferred electronicmessage delivery format.
 17. The non-transitory computer-usable mediumof claim 13, wherein said preferred message delivery format comprisesvoicemail data.
 18. The non-transitory computer-usable medium of claim17, wherein said preferred message delivery format comprises voicemaildata.
 19. The non-transitory computer usable medium of claim 13, whereinthe computer executable instructions are deployable to a client computerfrom a server at a remote location.
 20. The non-transitory computerusable medium of claim 13, wherein the computer executable instructionsare provided by a service provider to a customer on an on-demand basis.